Agentic UI: Combine create and blueprint onboarding into Build a new site#3859
Draft
shaunandrews wants to merge 2 commits into
Draft
Agentic UI: Combine create and blueprint onboarding into Build a new site#3859shaunandrews wants to merge 2 commits into
shaunandrews wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR simplifies the Agentic UI Add Site flow by combining the Empty Site and Blueprint options into a single “Build a new site” path.
Previously, users had to choose between “Create new” and “Start from a Blueprint” from the first screen. That split made the Empty Site path feel like a different kind of action from the Blueprint path, even though both are really ways to start building a new local WordPress site.
With this change, the first screen asks the broader question: do you want to build a new site or bring in an existing one? Once the user chooses “Build a new site,” the next screen lets them pick the starting point: an empty install, an uploaded Blueprint, or a featured Blueprint.
This keeps the decision closer to the available starting content, makes “Empty site” feel like one starting point among several, and reduces the number of top-level choices in the onboarding home.
The PR also fixes the Blueprint picker layout so long featured Blueprint lists can scroll properly. The onboarding shell now grows beyond the viewport instead of trapping overflow below the fold, while keeping the close control available during scrolling.
Proposed Changes
Testing Instructions
Related issues